<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7120/AI-Requirements-Starter-Kit.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7120</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7120&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>AI Requirements Starter Kit</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7120/AI-Requirements-Starter-Kit.aspx</link> 
    <description>&amp;ldquo;Let&amp;rsquo;s add AI&amp;rdquo; is not a requirement. It&amp;rsquo;s a vague wish that can turn into a costly prototype, a security headache, or an embarrassing production incident if the basics aren&amp;rsquo;t defined up front.&amp;nbsp;&amp;nbsp;Business Analysts are in the best position to prevent that outcome...
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 15 Dec 2025 00:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7120</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6951/Improve-the-User-Experience-with-Dialog-Maps.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6951</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6951&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Improve the User Experience with Dialog Maps</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6951/Improve-the-User-Experience-with-Dialog-Maps.aspx</link> 
    <description>Many books provide guidance on how to create effective user interface displays, a vital aspect of the user&amp;rsquo;s experience with a software application. But a user often must navigate through a series of screens to perform a task. Making that flow sequence logical and efficient is also an important part of the user experience.

I&amp;rsquo;m a big fan of analysis modeling, drawing diagrams that visually represent various aspects of a software system and its requirements. One of my favorite models is the dialog map, which provides a convenient way to represent, validate, and improve how a user navigates through a user interface.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 13 Jul 2025 23:31:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6951</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6745/Too-Many-Requirements.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6745</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6745&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Too Many Requirements?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6745/Too-Many-Requirements.aspx</link> 
    <description>A reader wrote to me with questions regarding a development project that he thought involved too many requirements and too little flexibility around requirement priorities. (You&amp;rsquo;ve never heard of such a thing before, right?)&amp;nbsp;
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Tue, 13 May 2025 01:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6745</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6541/Priming-A-Powerful-Tool-for-Business-Analysts.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6541</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6541&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Priming: A Powerful Tool for Business Analysts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6541/Priming-A-Powerful-Tool-for-Business-Analysts.aspx</link> 
    <description>Imagine walking into a store and hearing your favorite song playing in the background. Instinctively, you feel more at ease, more inclined to browse, and perhaps even to buy something. This subtle influence on your behavior is no accident&amp;mdash;it is an example of priming at work. Now, picture leveraging this same psychological phenomenon to enhance the effectiveness of business analysis. Welcome to the world of priming, where a well-placed word or image can shape perceptions, drive engagement, and ultimately lead to more successful projects.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 04 Aug 2024 04:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6541</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6370/The-Psychology-of-Requirements-Elicitation-Unraveling-the-Human-Factors.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6370</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6370&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Psychology of Requirements Elicitation: Unraveling the Human Factors</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6370/The-Psychology-of-Requirements-Elicitation-Unraveling-the-Human-Factors.aspx</link> 
    <description>Requirement elicitation, a critical part of project development, is often perceived as a purely technical process. However, this is not always the case. Effective requirement elicitation relies not only on technical acumen but also on an understanding of how human cognition, biases, and behaviors shape the process and what we can do to mitigate the negative influence of these inherent human factors. In this article, we selected three critical human factors: confirmation bias, the availability heuristic, and groupthink. These factors are commonly experienced in requirement elicitation activities. The article delves into the intricacies of these human aspects of requirement gathering and illustrates their impact using examples. We dissect the impact of these biases on requirement gathering, shedding light on the potential consequences that can arise when they go unchecked. Furthermore, we discuss strategies and techniques for mitigating these biases, emphasizing the role of requirements analysts as impartial facilitators.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 04 Feb 2024 06:08:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6370</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6291/5-Best-Elicitation-Techniques-to-use-in-2023.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6291</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6291&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>5 Best Elicitation Techniques to use in 2023</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6291/5-Best-Elicitation-Techniques-to-use-in-2023.aspx</link> 
    <description>There are several technological or stakeholder needs that are not officially listed but are of importance. Business analysts must identify the conditions necessary to access pertinent data; this is where elicitation techniques come into play.&amp;nbsp;&amp;nbsp;Elicitation is the foundation of every project because it puts the project&amp;#39;s requirements under the light. If elicitation is done wrong would lead to major failure and abandonment. Therefore, the elicitation process requires appropriate study and planning to prevent the likelihood of fatal errors impeding a project. But the question here is how can a business analyst gather requirements. In this article, we tell you the best elicitation techniques to collect information efficiently.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sat, 03 Jun 2023 20:36:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6291</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6111/How-to-remember-50-BABOK-Techniques.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6111</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6111&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to remember 50 BABOK Techniques</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6111/How-to-remember-50-BABOK-Techniques.aspx</link> 
    <description>BABoK v3 techniques are a lot. There are not just 10, 20, or 30 techniques but 50 techniques, to be precise and that&amp;#39;s not a small number!

The human mind can remember 5 to 7 elements at a time and anything more than that is hard to remember.

Then, how can one remember 50 techniques?

&amp;quot;Is it really possible to have a BABoK Techniques Mindmap?&amp;quot;

Many of you may wonder.

So, here&amp;#39;s the Ultimate BABoK techniques mindmap which could save you 40 hours of your International Institute of Business Analysis (IIBA) exam preparation!
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 19 Mar 2023 22:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6111</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6074/The-6-Most-Important-Requirements-Practices.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6074</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6074&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The 6 Most Important Requirements Practices</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6074/The-6-Most-Important-Requirements-Practices.aspx</link> 
    <description>There are many other valuable requirements activities besides these six. However, these practices greatly increase your chances of building a solution that achieves the desired business outcomes efficiently and effectively. Applying them doesn&amp;rsquo;t guarantee success for any BA, product owner, or product manager. But neglecting them likely ensures failure.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 12 Jun 2022 16:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6074</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5996/An-Overview-of-the-Underlying-Competency-of-Business-Knowledge.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5996</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5996&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>An Overview of the Underlying Competency of Business Knowledge</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5996/An-Overview-of-the-Underlying-Competency-of-Business-Knowledge.aspx</link> 
    <description>Business knowledge is simply knowing your business&amp;mdash;its facets, strengths, weaknesses, competition, challenges, positioning within the market, and readily available solutions to its daily problems.&amp;nbsp;Strong business knowledge should inform everything you do.&amp;nbsp;&amp;nbsp;So, what you learn and hear in discovery should be filtered through your business knowledge. What you define in your requirements should also be informed by your business knowledge. As one business analysis writer puts it, &amp;ldquo;I&amp;rsquo;ve always been of the opinion that I&amp;rsquo;d like to know as much as I can about whatever I can because you never know when something you learned may come in handy.&amp;rdquo;[2] The following four areas are the ones, specifically, according to BABOK, that you&amp;rsquo;ll want to apply yourself to.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 30 Jan 2022 20:04:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5996</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5926/Doing-Business-Analysis-in-a-Hybrid-World.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5926</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5926&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Doing Business Analysis in a Hybrid World</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5926/Doing-Business-Analysis-in-a-Hybrid-World.aspx</link> 
    <description>One of the biggest challenges now facing business analysts is this: how do we successfully engage with stakeholders, elicit requirements, and have productive workshops and meetings, without actually meeting in person? The tried-and-tested methods of getting together in a collaborative space, using sticky notes and whiteboards, and bribing attendees with baked goods, are no longer quite so straightforward in a world where some or all of the stakeholders are on the far end of an internet connection.

There are several factors to consider when moving out of the purely physical realm as a business analyst.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 10 Oct 2021 05:04:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5926</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5914/Root-Cause-Analysis-Using-a-Fishbone-Diagram-and-the-Five-Whys.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5914</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5914&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Root Cause Analysis Using a Fishbone Diagram and the Five Whys</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5914/Root-Cause-Analysis-Using-a-Fishbone-Diagram-and-the-Five-Whys.aspx</link> 
    <description>I was teaching a business analysis course recently and noted that few students had used a Fishbone Diagram along with the Five Whys for root cause analysis. This motivated me to write an article on root cause analysis using the combo method along with a short example.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 12 Sep 2021 08:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5914</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5817/How-to-overcome-the-common-elicitation-challenges-a-Business-Analyst-faces.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5817</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5817&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to overcome the common elicitation challenges a Business Analyst faces</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5817/How-to-overcome-the-common-elicitation-challenges-a-Business-Analyst-faces.aspx</link> 
    <description>What are the most common elicitation challenges? This is one of the most discussed topics from my business analysis training sessions. A business analyst extracts information in various forms, from various sources, and transforms those findings into requirements and design artifacts. Let&amp;rsquo;s take a look at some of the common challenges during the elicitation process and how to address them.
</description> 
    <dc:creator>Swatipitre</dc:creator> 
    <pubDate>Wed, 19 May 2021 18:26:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5817</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5834/Integration-Requirement-Analysis-Framework.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5834</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5834&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Integration Requirement Analysis Framework</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5834/Integration-Requirement-Analysis-Framework.aspx</link> 
    <description>Integration requirements are critical for any Project&amp;rsquo;s success when Business Processes flow across multiple systems. As a Business Analyst it&amp;rsquo;s our responsibility to understand the end-to-end Business and Systems Process flow and document the hand off as part of the requirements gatherings process. A systematic approach to gather the requirements for integration between systems will ensure that there is a smooth interaction between the systems and hence the Business Process flow. The below Framework on Integration Requirements Analysis provides a systematic approach to document requirements for an Integration Project
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 17 May 2021 00:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5834</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5769/Tasks-Mapped-To-Artifacts.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5769</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5769&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Tasks Mapped To Artifacts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5769/Tasks-Mapped-To-Artifacts.aspx</link> 
    <description>The intention of this article is to identify and specify the artifacts listed in the BABOK. These artifacts are listed within the Outputs section of the BABOK tasks. Outputs are described by a paragraph of text within each task. In this article I attempted to expand on these descriptions by adding detail to their content.

It is assumed that each activity produces a tangible output[2]&amp;nbsp;which is consistent with the layout of the BABOK. Those outputs are classed as artifacts with attributes. Each artifact&amp;rsquo;s attribute description is taken from the element description of the tasks that output that artifact. The BABOK element descriptions provide guidelines for activity that produces the attribute, without necessarily defining the information contained in the attribute.That information has been derived from the element description.

Artifacts are derived from the BABOK Output sections. Artifact attributes are derived from the BABOK Element sections. A useful addition to the BABOK might be examples or templates of the outputs.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 07 Feb 2021 21:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5769</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5603/Remote-Business-Analysis-Interviewing-and-Facilitating.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5603</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5603&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Remote Business Analysis: Interviewing and Facilitating</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5603/Remote-Business-Analysis-Interviewing-and-Facilitating.aspx</link> 
    <description>Business people call remote meetings virtual or on-line sessions, or simply conference calls. For many years we have been utilizing this form of communications to save time and money. Due to the global virus pandemic, remote meetings are now not just convenient, but a necessity for maintaining social distancing. Fortunately we have technology that assists us in managing these remote sessions to not only hear the stakeholders, but see them as well. However, remote stakeholder interviewing and meetings have their additional challenges beyond face-to-face encounters. Regardless of the technology used, we need to be keenly aware of these additional negative risks and pursue mitigations.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 07 Sep 2020 05:16:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5603</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5590/Strategy-to-Pass-the-IIBA-AAC-Exam.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5590</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5590&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Strategy to Pass the IIBA-AAC Exam</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5590/Strategy-to-Pass-the-IIBA-AAC-Exam.aspx</link> 
    <description>While the IIBA-AAC exam is not the most challenging exam that I&#39;ve ever taken, it does require you to have a very specific type of understanding of the Agile Extension to the BABOK Guide. Though it&#39;s not a requirement, I recommend taking an exam prep course to increase your chances of passing the exam. Those who did not initially pass the exam reported that they underestimated the exam and figured that they would be able to rely on their agile experience to pass the exam. WRONG!! In fact, the exam doesn&#39;t focus much on the details of agile ceremonies or daily activities, but more so on the general principles of agile business analysis.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 04 May 2020 02:44:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5590</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5554/Clean-Language-in-Business-Analysis-Interviewing-and-Facilitating.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5554</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5554&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Clean Language in Business Analysis: Interviewing and Facilitating</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5554/Clean-Language-in-Business-Analysis-Interviewing-and-Facilitating.aspx</link> 
    <description>&amp;nbsp;&amp;ldquo;Clean Language&amp;rdquo; is a conversation technique developed by a psychotherapist, David Grove. It is a method of asking neutral questions to avoid influencing patient responses.  Besides psychotherapy, clean language can be used in various fields for interviewing and facilitating meetings with stakeholders. This is particularly true for business analysis. The context of this article is interviewing and facilitating meeting with a focus on using clean language to ensure that stakeholder requirements are captured without the influence of the business analyst. In this article, you will note that I have cited several sidebar comments to help the reader connect the dots with various business analysis aspects.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Thu, 30 Apr 2020 01:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5554</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5502/Inversion-Mental-Models-for-Business-Analysts-Part-III.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5502</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5502&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Inversion (Mental Models for Business Analysts, Part III)</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5502/Inversion-Mental-Models-for-Business-Analysts-Part-III.aspx</link> 
    <description>Learning about mental models and how to apply them to their work is one of the best investments for business analysts interested in achieving the level of deep thinking that leads to better outcomes for their projects and organizations.&amp;nbsp;&amp;nbsp;There is incredible power in using inversion at the outset of a project to imagine ourselves in a future where the solution has not only been delivered, but is in the hands of end-users to get their job done. Rather than simply going through the typical project phases in forward motion, we can then look backward and gain additional perspective into what might go wrong so that preventive steps can be taken to avoid those bad outcomes.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 12 Jan 2020 14:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5502</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5355/Creating-a-Culture-That-Respects-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5355</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5355&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Creating a Culture That Respects Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5355/Creating-a-Culture-That-Respects-Requirements.aspx</link> 
    <description>Culture clashes frequently arise when teams are working on requirements. There are those who recognize the many risks associated with trying to develop software based on minimal or telepathically communicated requirements. Then there are those who think requirements are unnecessary. It can be tough to gain business-side cooperation on projects like legacy-system replacement if users see this as unrelated to their own business problems and not worth their time. Understanding why people resist participating in requirements development is the first step to being able to address it.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 27 May 2019 16:19:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5355</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5347/Requirements-In-Context-Part-3-Scope-High-Level-Requirements.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5347</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5347&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements In Context Part 3: Scope = High-Level Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5347/Requirements-In-Context-Part-3-Scope-High-Level-Requirements.aspx</link> 
    <description>
Project Scope.&amp;nbsp;We will see how scope&amp;nbsp;statements, when making reference to&amp;nbsp;business functionality, lead directly to&amp;nbsp;High-Level&amp;nbsp;requirements.&amp;nbsp; Gathering requirements for a business information system is&amp;nbsp;most often&amp;nbsp;done within the context of a project.&amp;nbsp;Approval of a project&amp;nbsp;includes its&amp;nbsp;sponsors&amp;nbsp;signing off&amp;nbsp;on its scope.&amp;nbsp;The&amp;nbsp;scope&amp;nbsp;for a business information system project is&amp;nbsp;typically&amp;nbsp;defined in&amp;nbsp;functional&amp;nbsp;terms.&amp;nbsp;Items in scope make reference to (or should make reference to)&amp;nbsp;business functions, processes and/or activities&amp;nbsp;that are to be delivered.

</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 05 May 2019 20:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5347</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5236/Requirement-Elicitation-Stories-Are-Not-Requirements.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5236</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5236&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirement Elicitation: Stories Are Not Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5236/Requirement-Elicitation-Stories-Are-Not-Requirements.aspx</link> 
    <description>One of the three activities encompassed under Requirements Analysis is the process of &amp;lsquo; Requirements elicitation&amp;rsquo;. IIBA&amp;rsquo;s definition of &amp;lsquo;elicitation&amp;rsquo; is &amp;ldquo;An activity within requirements development that identifies sources for requirements and then uses elicitation techniques to gather requirements from those sources.&amp;rdquo;

However, this definition appears incomplete from an analyst&amp;rsquo;s point of view as it relies solely on the assumption that one can come up with requirements only by running elicitation techniques; however, the process of elicitation is not as simple and straightforward as it seems. Let&amp;rsquo;s see why.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 17 Mar 2019 06:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5236</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5217/Stakeholder-Interviewing-and-Facilitated-Meetings-steps-for-eliciting-requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5217</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5217&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Stakeholder Interviewing and Facilitated Meetings: steps for eliciting requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5217/Stakeholder-Interviewing-and-Facilitated-Meetings-steps-for-eliciting-requirements.aspx</link> 
    <description>This article provides high-level steps for eliciting requirements when interviewing or holding a facilitated meeting with stakeholders; it was motivated by an attendee question at a recent Modern Analyst webinar: &amp;ldquo;Functional vs. Nonfunctional requirements.&amp;rdquo;&amp;nbsp;&amp;nbsp;The question was, &amp;ldquo;Can a Business Analyst elicit functional and nonfunctional requirements in the same iteration?&amp;rdquo;&amp;nbsp;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Tue, 01 Jan 2019 05:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5217</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5144/Managing-Requirements-is-an-Art-Mastered-by-a-Business-Analyst.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5144</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5144&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Managing Requirements is an Art Mastered by a Business Analyst</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5144/Managing-Requirements-is-an-Art-Mastered-by-a-Business-Analyst.aspx</link> 
    <description>In a classic business analyst universe, requirements are the soul of all the work a business analyst does. If a business analyst fails to identify and translate the right requirements, they&amp;rsquo;re out of a job. This is the reason why a successful business analyst is always good at requirements handling/management process.
What makes requirements an essential part of a BA&amp;rsquo;s job?
For a business analyst, requirements are defined as the logical and essential steps which needs to be fulfilled in order to achieve a successful end-state or a solution to a stakeholder&amp;rsquo;s business problem. These requirements drive the solution and are the key elements of any successful solution implementation. Business analysts are the ones who not only ensures the expected solution is delivered, but they&amp;rsquo;re also the owner of the requirements handling/management process. Business analysts identify the right requirements and help them convert into a form consumable by delivery teams to deliver the expected outcome in a timely manner. 
The requirements management/handling process consists of 4 basic steps: Discovery, Analyze, Draft and Implement.
1.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Discovery
Requirements discovery is a phase in which we identify, gather and scope the requirements. This phase builds the basic requirements framework for delivery. To identify and gather requirements, a business analyst uses various requirements elicitation techniques like observation, shadowing, protocol analysis, apprenticeship, prototyping, focus groups, scenario&amp;rsquo;s, background research and many others. These techniques are aimed towards gathering information related to a business problem and/or a solution that business stakeholders are trying to achieve.
Requirements identification is a highly interactive activity, which relies on the involvement of the right stakeholders. Elicitation activities continue while a business analyst traverse through other stages/steps of requirements gathering.
It is very important for a business analyst to not only identify but to scope the requirement. Requirements are driven by information collected by various elicitation methods; however, the relevancy of the requirement needs to be determined.
The simplest way to do so is to perform some of the elicitation techniques repetitively. Look for facts via secondary support of documents or information from another source just to verify. Chart your scope based on the overall direction of the information flow and the end-state which stakeholders are trying to achieve. 
Scoping cannot be definitive in the business analyst&amp;rsquo;s landscape. It&amp;rsquo;s a loose boundary which needs to be flexible enough to account for other business or priority changes. Loose boundaries do help the business analyst in defining a playground where they need to operate for a successful outcome.
2.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Analyze
The most important activity of the requirements handling process is to analyze a requirement. Analyzing a requirement will provide us with a definite outcome along with the complete information on achieving that outcome. There can be various types of analysis like strategic analysis, functional and technical analysis. 
Strategic analysis is performed by understanding the strengths, weakness, opportunities and threats provided by implementing this requirement. It helps a business analyst to understand the priority and criticality of the requirement which also determines how essential it is for a business to implement those requirements.
Functional analysis provides an ability to understand the requirement from the end user perspective.&amp;nbsp; It is performed by interacting with people who&amp;rsquo;re impacted by the implementation of requirements. This provides unique opportunity for a business analyst to shape the solution in a way that accommodates the minimal, easy to adapt change to the end users or the impacted.
Technical analysis is performed by further breaking down functional requirements into a series of small implementation steps which a delivery person can understand. It is the delivery person/team who needs to deliver the technical solution. It is important to not miss any aspect of functional requirement to be translated into technical requirements which is a supporting pillar for successful solution implementation.
Depending upon the type of analysis, we determine the type of requirement. Upon successfully analyzing and understanding the type of requirement we start drafting requirements into various artifacts.
3.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Draft
Once a business analyst has understood the type of requirements and its expected outcome, business analyst can draft those requirements in their respective artifacts. There&amp;rsquo;re various artifacts such as business requirements document and/or specification requirements document and user stories which are authored and owned by a business analyst while there&amp;rsquo;re some other like project charter, technical design document or anything alike to which a business analyst contributes actively. Drafting of requirements take the utmost time as the translation needs clarifications and numerous back and forth interactions. Once a requirement drafting is complete, it&amp;rsquo;s time to walk them through with the entire team.
4.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Implement
The first step of requirements implementation is to arrange for a walk-through of freshly drafted requirements where the audience includes all stakeholders including delivery team. This walk-through session helps with course correction of requirements if there&amp;rsquo;s a miss while drafting them. Also, requirements walkthrough is a common platform where in the stakeholders and other team members have the opportunity to ensure alignment of the requirements to the desired end state. Once the requirements are defined and finalized, business analysts have to ensure continuous requirement refinement for successful delivery.
This is the final step of requirements management process. Once the requirement has been identified, scoped, analyzed, drafted and confirmed, business analysts have to keep their eye out for on-going business changes, these changes may affect any of the existing requirements and their desired outcomes. As business changes are constant, the impacts on the already drafted requirements is constant. There is a small deviation of requirements which can still be managed by refining the requirement and updating them, but then if the deviation requires additional effort for which the cost involved is high, then changes are to be considered for enhancement. This decision must be evaluated by a business analyst before taking appropriate actions accordingly.
At this stage, all the requirements are the guiding principle for the delivery team to deliver the solution. Requirements Handling/Management Process is the one, a business analyst has to master to be considered as successful.



Author: Nimil Parikh, Business Analyst


Nimil Parikh is a new generation business analyst who transforms business processes by leveraging IT tools and applications. He has over 7 years of experience modeling, analyzing, measuring, improving, optimizing and automating business processes. He adds value by his ability to context switch while providing cross-functional business solution and ensuring timely delivery by managing and streamlining business processes and driving strategic leadership. He is known to introduce IT business transformation and ensure successful implementation. Nimil possess MBA from San Jose State university, MBA Marketing and Information technology engineering from India. Nimil lives in Campbell, California. He enjoys challenges and believes in making things right. Reach him via email &amp;ndash; parikhnimil@yahoo.co.in
&amp;nbsp;

</description> 
    <dc:creator>Nimil Parikh</dc:creator> 
    <pubDate>Sun, 21 Oct 2018 21:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5144</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5111/Practical-Approach-To-Elicit-Requirements-Successfully.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5111</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5111&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Practical Approach To Elicit Requirements Successfully</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5111/Practical-Approach-To-Elicit-Requirements-Successfully.aspx</link> 
    <description>Project statistics state that most project rework/failure is due to incomplete/improper/unclear requirements, hence the role the Business Analyst becomes even more critical as they shoulder a huge responsibility of eliciting and collaborating with the stakeholders to obtain clear, concise and complete requirements.&amp;nbsp; The elicitation and collaboration knowledge area focuses on drawing forth or receiving information from stakeholders and other sources by directly interacting with stakeholders, researching topics, experimenting or simply being handed information.</description> 
    <dc:creator>Roshini</dc:creator> 
    <pubDate>Sun, 16 Sep 2018 20:18:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5111</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5083/Lets-explore-Business-Analysts-Toolbox.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5083</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5083&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Let&#39;s explore Business Analysts&#39; Toolbox</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5083/Lets-explore-Business-Analysts-Toolbox.aspx</link> 
    <description>Chaos! Stress! Everyday mess! Isn&amp;rsquo;t this an everyday situation for a business analyst? If not, either you&amp;rsquo;ve job satisfaction or you&amp;rsquo;re not being introduced to the real world of business analysis.
A person might possess great skills, however, (s)he might not be able to utilize skills without the right mix of tools and environment. A toolbox enables a person to implement the skills in the most efficient way. Possessing necessary tools is just the one part of it. Another is the knowledge to utilize the right tools at the right time to cater the solution and ensure timely committed delivery.
What are these tools? How do we map the usage of tools to the given circumstance? How can we efficiently utilize the tool? Does it depend on the solution or the approach?</description> 
    <dc:creator>Nimil Parikh</dc:creator> 
    <pubDate>Sun, 08 Jul 2018 12:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5083</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4905/How-are-top-performing-business-analysts-different-than-an-average-BA.aspx#Comments</comments> 
    <slash:comments>11</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=4905</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=4905&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How are top-performing business analysts different than an average BA?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4905/How-are-top-performing-business-analysts-different-than-an-average-BA.aspx</link> 
    <description>During a recent presentation to business analysts, I used one of my consulting projects as an example of how to apply an analysis technique we were discussing. A member of the audience asked,&amp;nbsp;&amp;ldquo;What made this company hire you as a BA consultant to tackle this project, when they already have so many in-house product managers and business analysts on their teams?&amp;rdquo;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 05 Feb 2018 01:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:4905</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3820/Validating-a-Strategic-Project-at-the-Enterprise-Level.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3820</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3820&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Validating a Strategic Project at the Enterprise Level</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3820/Validating-a-Strategic-Project-at-the-Enterprise-Level.aspx</link> 
    <description>Prior to proceeding with a strategic project, project leadership needs to ensure that the project&amp;nbsp;still:


    aligns with the direction of the business entity, and
    fits the needs of the targeted customer segment,
    as it did when the project was an initiative. This brief article starts at the inception of an initiative during Enterprise Analysis to the validation of a strategic project prior to kickoff. Note in this article, I include both the private and public sectors when I use the terms such as &amp;ldquo;business entity&amp;rdquo; and &amp;ldquo;customer segments.&amp;rdquo;
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 01 Oct 2017 22:08:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3820</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3811/Ground-Rules-Distractions.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3811</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3811&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Ground Rules &amp; Distractions</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3811/Ground-Rules-Distractions.aspx</link> 
    <description>Ground rules are essential for any meeting. It may be what makes the meeting a success or failure. As a Business Analyst we are constantly organizing and facilitating meetings of various sizes to progress through the SDM (System Design Methodology) for a project. It is important that all sponsors and participants of the project understand what to expect from the upcoming meetings to be organized. Ground rules are generally discussed during the kickoff meeting, documented, and then displayed moving forward.</description> 
    <dc:creator>tommcintire</dc:creator> 
    <pubDate>Tue, 08 Aug 2017 04:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3811</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3744/5-Tips-for-Success-with-Packaged-Solution-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3744</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3744&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>5 Tips for Success with Packaged Solution Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3744/5-Tips-for-Success-with-Packaged-Solution-Requirements.aspx</link> 
    <description>A common challenge of enterprise Business Analysts is the discovery, understanding, and description of requirements in the context of implementing packaged solutions. Management assigns us to projects with a predefined solution, and we struggle to figure our role when there seems to be no significant build activity. What are we supposed to do in this situation when there seems to be no need to produce standard requirement deliverables?

&amp;nbsp;

Put a typical Business Analyst in this environment and do not be surprised to hear the phrase &amp;ldquo;I&amp;rsquo;m not sure of my role.&amp;rdquo; Why do packaged solution projects cause discomfort?
</description> 
    <dc:creator>michael_r_roy01</dc:creator> 
    <pubDate>Wed, 29 Mar 2017 18:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3744</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3726/Differences-Duties-and-Responsibilities-of-Business-Analysts-and-System-Analysts.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3726</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3726&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Differences, Duties and Responsibilities of Business Analysts and System Analysts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3726/Differences-Duties-and-Responsibilities-of-Business-Analysts-and-System-Analysts.aspx</link> 
    <description>A business analyst is a person who analyzes, organizes, explores, scrutinizes and investigates an organization and documents its business and also assesses the business model and integrates the whole organization with modern technology. The Business Analyst role is mostly about documenting, verifying, recording and gathering the business requirements and its role is mostly associated with the information technology industry.</description> 
    <dc:creator>Bhairav24</dc:creator> 
    <pubDate>Sun, 19 Mar 2017 21:50:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3726</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3684/Alice-in-Wonderland-Meet-Wonderlands-Stakeholders-Episode-4.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3684</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3684&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>“Alice in Wonderland”: Meet Wonderland’s Stakeholders, Episode 4</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3684/Alice-in-Wonderland-Meet-Wonderlands-Stakeholders-Episode-4.aspx</link> 
    <description>Moving on, we will investigate the importance of the business analyst&amp;rsquo;s often delicate relationship with individual stakeholders. &amp;nbsp; A business analyst is a facilitator of change, and in affecting these changes within a company, the analyst must interact with multiple stakeholders of varying personalities. When identifying and delivering the necessary changes within a business, the analyst must develop and maintain a relationship with each individual stakeholder. &amp;nbsp;Each stakeholder will wield a different level of authority within the company and hold a certain amount of power over those changes that are coming into effect. Noting this, the analyst must take part in a careful balancing act, juggling these relationships in order to facilitate change with minimal difficulty.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 11 Dec 2016 21:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3684</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3641/When-Requirements-Elicitation-Becomes-a-Mad-Tea-Party.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3641</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3641&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>When Requirements Elicitation Becomes a “Mad Tea Party”!</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3641/When-Requirements-Elicitation-Becomes-a-Mad-Tea-Party.aspx</link> 
    <description>The difficulty of gathering information and establishing requirements, owing to the chaotic nature of the business world, is clear to see. Every business analyst must overcome their own Mad Tea Party if they are to be successful in carrying out their mission. As Alice is confronted with the unreliability of the Hatter, the March Hare, and the Dormouse, so too is the analyst faced with unreliable stakeholders. In her attempts to gain an understanding of the never-ending tea party, Alice&amp;rsquo;s use of elicitation is effectively useless in the face of endless riddles, an unconventional sense of time, and undependable characters. &amp;nbsp;Analysts find themselves in comparable environments with various degrees of chaos and unpredictability.&amp;nbsp;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 10 Oct 2016 01:06:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3641</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3251/Requirements--Prerequisites.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3251</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3251&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements - Prerequisites</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3251/Requirements--Prerequisites.aspx</link> 
    <description>Often I come across situations where a BA is unprepared or under-prepared in approaching the requirements elicitation process. This leads to irritated business users, incomplete requirements, significant delays, reworks, and poor opinion about BA&#39;s in general. I decided to put together a list of prerequisites that a BA must complete before commencing requirements elicitation process.</description> 
    <dc:creator>ManiRamasarma</dc:creator> 
    <pubDate>Thu, 21 Jul 2016 13:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3251</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3545/The-Power-of-a-Question.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3545</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3545&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Power of a Question</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3545/The-Power-of-a-Question.aspx</link> 
    <description>To be a great analyst, you&amp;rsquo;ll need to ask great questions. In order to ask great questions, you&amp;rsquo;ll need to remain inquisitive. &amp;nbsp;Fact of the matter is, that if you are performing any kind of analysis, you need to become very comfortable with asking difficult questions. Questions that make people uncomfortable and questions that might even potentially expose unpopular answers.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 06 Jun 2016 01:53:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3545</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3367/Customer-Journey-Mapping-for-Business-Analysts.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3367</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3367&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Customer Journey Mapping for Business Analysts </title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3367/Customer-Journey-Mapping-for-Business-Analysts.aspx</link> 
    <description>Customer journey mapping is a great way to understand your customer intimately to provide insights into providing targeted customer experience that empower the customer positively to drive better business outcomes. &amp;nbsp;This technique places the customer first with a deep emotional understanding, then looks backwards toward the experiences provided by the operating model, thus enabling good aspects to be reinforced and negative ones to be managed. It provides a complete 360 end to end experience of the customer to be realized driving customer insights, allowing more blue sky approaches to offsetting emotional deficits...</description> 
    <dc:creator>pomifritz</dc:creator> 
    <pubDate>Sun, 29 Nov 2015 21:52:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3367</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3369/The-Mystery-of-the-Missing-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3369</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3369&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Mystery of the Missing Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3369/The-Mystery-of-the-Missing-Requirements.aspx</link> 
    <description>This is a story of an outsourced product implementation contract between two companies, FinCo and ProdCo. What started out as an exciting contract turned out to be a bitter experience for both the companies. There are lessons to be learnt from this story &amp;ndash; about outsourced contracts, about setting expectations and above all, about good old business requirements.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 01 Nov 2015 20:38:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3369</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3250/Offering-Less-Gets-You-More-When-Interviewing.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3250</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3250&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Offering Less Gets You More When Interviewing</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3250/Offering-Less-Gets-You-More-When-Interviewing.aspx</link> 
    <description>The scenario is simple: You&amp;rsquo;ve been tasked to determine the requirements for a new project. You&amp;rsquo;ve done your homework by reviewing existing documentation. And, now, you&amp;rsquo;ve arranged to have a meeting with a Subject Matter Expert (SME).
So, where does one begin on this path to enlightenment? When you talk to the SME for the first time, do you start by outlining everything that you think you&amp;rsquo;ve learned already?</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 26 Oct 2015 01:50:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3250</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3357/Gain-your-Stakeholders-Attention-with-this-Marketing-Technique.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3357</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3357&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Gain your Stakeholder&#39;s Attention with this Marketing Technique</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3357/Gain-your-Stakeholders-Attention-with-this-Marketing-Technique.aspx</link> 
    <description>The first step to solve a problem is to frame it correctly. These aren&amp;rsquo;t the right questions to ask. The real question these BAs should be asking is, &amp;ldquo;how do I get my stakeholders to stay involved throughout the requirements process, so I can have their input at the right times during requirements discovery, analysis, and validation?&amp;rdquo;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 05 Oct 2015 09:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3357</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3325/Rationale-for-Rationale.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3325</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3325&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Rationale for Rationale</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3325/Rationale-for-Rationale.aspx</link> 
    <description>This is the eleventh in a series that explains the thinking behind the Volere requirements techniques&amp;mdash; previous and future articles explore aspects of applying these techniques in your environment.

This article focuses on the often-asked question: why, when I ask for requirements, do people give me solutions and what can I do to get the real requirement?</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 17 Aug 2015 04:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3325</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3297/Ensuring-Success-for-Projects-Driven-by-User-Needs.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3297</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3297&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Ensuring Success for Projects Driven by User Needs</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3297/Ensuring-Success-for-Projects-Driven-by-User-Needs.aspx</link> 
    <description>Solution Anthropology encompasses the work of anyone who works directly with the end users so the work is coordinated and consistent. Therefore Solution Anthropology is not one role, but a team of people with the responsibility to delight the end user and a broad skill set to accomplish just that.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 27 Jul 2015 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3297</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3298/Add-Observation-to-Your-Business-Analysis-Toolkit.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3298</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3298&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Add Observation to Your Business Analysis Toolkit</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3298/Add-Observation-to-Your-Business-Analysis-Toolkit.aspx</link> 
    <description>Observation as a tool is used to understand people and their environments. It is a tool best used not in situations where we are verifying fairly well-understood information, but rather in situations where we do not really know what we are looking for. Observation is not about validating assumptions, but rather is a tool to find out what we don&amp;rsquo;t know that we don&amp;rsquo;t know. Observation should bring out the surprising and the unexpected. Of course observation has a purpose. But the purpose can be fairly broad.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 15 Jun 2015 04:35:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3298</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3155/The-Fuzzy-Line-between-Requirements-and-Design.aspx#Comments</comments> 
    <slash:comments>4</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3155</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3155&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Fuzzy Line between Requirements and Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3155/The-Fuzzy-Line-between-Requirements-and-Design.aspx</link> 
    <description>People sometimes say that requirements are about &amp;ldquo;what&amp;rdquo; and design is about &amp;ldquo;how.&amp;rdquo; There are two problems with this simplistic demarcation. &amp;nbsp;This makes it sound as though there&amp;rsquo;s a sharp boundary between requirements and design. There&amp;rsquo;s not. In reality, the distinction between requirements and design is a fuzzy gray area, not a crisp black line. I prefer to say that requirements should emphasize &amp;ldquo;what&amp;rdquo; and design should emphasize &amp;ldquo;how.&amp;rdquo;&amp;nbsp;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 13 Apr 2015 10:47:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3155</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3207/Getting-Back-to-Basics-Asking-the-Right-Questions.aspx#Comments</comments> 
    <slash:comments>8</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3207</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3207&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Getting Back to Basics: Asking the Right Questions</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3207/Getting-Back-to-Basics-Asking-the-Right-Questions.aspx</link> 
    <description>Maybe it&amp;rsquo;s time to get back to the basics behind requirements and why we need them.&amp;nbsp;In this 3-piece article series, we are getting back to the basics of requirements. Our first installment addresses how to ask the right questions.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 02 Mar 2015 10:25:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3207</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2929/Revealing-Invisible-Requirements.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2929</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2929&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Revealing Invisible Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2929/Revealing-Invisible-Requirements.aspx</link> 
    <description>No matter how thorough a job you do on requirements elicitation, there is no way to be certain that you have found them all. No little green light comes on to announce &amp;ldquo;You&amp;rsquo;re done!&amp;rdquo; You should always plan on new requirements trickling in throughout the project. However, an excessive rate of change of requirements suggests that important requirements were overlooked during elicitation.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 31 Mar 2014 04:27:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2929</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1420/An-Overview-of-Website-Requirements-Basics.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1420</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1420&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>An Overview of Website Requirements Basics</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1420/An-Overview-of-Website-Requirements-Basics.aspx</link> 
    <description>Prior to the creation of something as potentially complex and ubiquitous of a website, an analyst must create a thorough, precise set of requirements in consultation with the right subject matter experts and business stakeholders. But unless one is armed with the proper planning procedures and techniques, the prospect of creating requirements for something as vast as an online business presence or functioning e-commerce system (or both) can be intimidating.</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Fri, 21 Feb 2014 10:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1420</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2483/The-Top-Five-Go-To-Requirements-Elicitation-Methods.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2483</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2483&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Top Five Go-To Requirements Elicitation Methods</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2483/The-Top-Five-Go-To-Requirements-Elicitation-Methods.aspx</link> 
    <description>There are a myriad of requirements elicitation methods. The BABOK lists nine (Brainstorming, Document Analysis, Focus Groups, Interface Analysis, Interviews, Observation, Prototyping, Requirements Workshops, Survey/Questionnaire), but there are many more methods out there such as protocol analysis , job application design , and so on).
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Wed, 25 Sep 2013 14:38:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2483</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2644/Interaction-Skills-for-the-Business-Analyst.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2644</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2644&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Interaction Skills for the Business Analyst</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2644/Interaction-Skills-for-the-Business-Analyst.aspx</link> 
    <description>Interaction skills are a soft skill set that includes tactful communication, mediation, and diplomacy. BABOK divides interaction skills into three broad areas: facilitation and negotiation, leadership and influencing, and teamwork. All of these skills encompass the ability to navigate politics, even in tricky territory, in order to bring people together in consensus on a project, to mitigate conflicts, and to help people feel heard.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Thu, 22 Aug 2013 07:02:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2644</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2214/The-Myth-of-the-On-Site-Customer.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2214</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2214&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Myth of the On-Site Customer</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2214/The-Myth-of-the-On-Site-Customer.aspx</link> 
    <description>In an ideal world, a single, full-time, expert user would indeed be sitting within view—“on sight”—of developers, ready at a moment’s notice to speak definitively for the entire user community. In reality, this is unlikely in most situations.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 19 Aug 2013 04:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2214</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2663/Can-business-analysis-help-finding-the-missing-requirements.aspx#Comments</comments> 
    <slash:comments>4</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2663</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2663&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Can business analysis help finding the “missing” requirements?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2663/Can-business-analysis-help-finding-the-missing-requirements.aspx</link> 
    <description>As Business Analysts, we are involved in requirements development and management day in and day out with most of the time spent on eliciting, analyzing and specifying business and software requirements for multiple projects. We follow or adopt multiple frameworks, approaches and tools that help us to successfully gather and analyze requirements. Having done all these things to ensure the success of the projects, we still end up in a few projects wherein we have “missed” few requirements.</description> 
    <dc:creator>umbreen</dc:creator> 
    <pubDate>Wed, 03 Jul 2013 04:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2663</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2442/The-Whole-Requirement-and-Nothing-But-the-Requirement.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2442</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2442&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Whole Requirement and Nothing But the Requirement</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2442/The-Whole-Requirement-and-Nothing-But-the-Requirement.aspx</link> 
    <description>&amp;#160;It is wise to use whatever techniques we can to discover the &#39;real&#39; requirements and business rules before embarking on development. We all seem to know that it is cheaper to fix problems earlier rather than later in an IT project. So why do so many of our projects exhibit the same mistakes?</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Wed, 30 Jan 2013 10:23:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2442</guid> 
    
</item>

    </channel>
</rss>